Authentication of medication delivery vehicle to facilitate medication release

ABSTRACT

A delivery device includes a circuit for receiving an authentication signal. The delivery device contains a substance encapsulated therein. The delivery device determines whether a user is authenticated based upon the authentication signal and an identifier stored within the delivery device. The delivery device heats, responsive to determining that the user is not authenticated within a predetermined time period after the delivery device being ingested by the user, the substance encapsulated within the delivery device.

TECHNICAL FIELD

The present invention relates generally to a method, system, andcomputer program product for authentication of a medication deliveryvehicle. More particularly, the present invention relates to a method,system, and computer program product for authentication of a medicationdelivery vehicle with a user to facilitate release of medicationcontained therein.

BACKGROUND

Many medications are expensive to purchase, have significant streetvalue, and are often stolen or otherwise obtained for the purpose ofreselling. Additionally, as patients become increasingly memorychallenged due to age or illness, health aids, domestic aids, and otherservice providers may be necessary to assist in administeringmedications to the patient. For example, the service provider may assista patient in administering medication in patient's home and/or in anassisted living facility in which the patient resides. Unfortunately,the service provider may substitute a different medication for theintended medication either accidently or purposely in order to keep orsell the medication. This type of abuse often goes unrecognized.Accordingly, a need exists to authenticate a medication to ensure that apatient receives only the medication that has been prescribed to thepatient.

Published and web-based reference sheets are available including anumber of medications to allow a patient to look up and visuallyidentify a particular medication prior to taking the medication. Thesereference sheets typically include an image of a particular pill orother medication showing one or more of a shape, color, and marking ofthe pill. However, looking up the particular medication that the patienthas been prescribed is a time consuming process. A typical patient willstop at the color or size, and can be easily convinced that a differentlooking pill is a new version of the pill even when such may not be thecase. In addition, securing medication by locking the medication withina storage requires diligence and introduces the risk of the patientforgetting to take the medication due to the medication no longer beingwithin sight of the patient.

SUMMARY

The illustrative embodiments provide a method, system, and computerprogram product. An embodiment of a method includes monitoring, by acircuit of a delivery device, for receiving an authentication signal. Inthe embodiment, the delivery device contains a substance encapsulatedtherein. In the embodiment, the method further includes determiningwhether a user is authenticated based upon the authentication signal andan identifier stored within the delivery device. In the embodiment, themethod further includes heating, responsive to determining that the useris not authenticated within a predetermined time period after thedelivery device being ingested by the user, the substance encapsulatedwithin the delivery device.

An embodiment includes a computer program product. The computer programproduct includes one or more computer-readable storage devices, andprogram instructions stored on at least one of the one or more storagedevices.

An embodiment includes a computer system. The computer system includesone or more processors, one or more computer-readable memories, and oneor more computer-readable storage devices, and program instructionsstored on at least one of the one or more storage devices for executionby at least one of the one or more processors via at least one of theone or more memories.

BRIEF DESCRIPTION OF THE DRAWINGS

Certain novel features believed characteristic of the invention are setforth in the appended claims. The invention itself, however, as well asa preferred mode of use, further objectives and advantages thereof, willbest be understood by reference to the following detailed description ofthe illustrative embodiments when read in conjunction with theaccompanying drawings, wherein:

FIG. 1 depicts a block diagram of a network of data processing systemsin which illustrative embodiments may be implemented;

FIG. 2 depicts a block diagram of a data processing system in whichillustrative embodiments may be implemented;

FIG. 3 depicts a block diagram of an embodiment of a medication deliveryvehicle (MDV) in accordance with an illustrative embodiment;

FIG. 4 depicts a block diagram of an example scenario for authenticationof a medication delivery vehicle (MDV) within a simplified upperdigestive tract of a user in accordance with an illustrative embodiment;

FIG. 5 depicts a flowchart of an example process for authentication of amedication delivery vehicle (MDV) in accordance with an illustrativeembodiment; and

FIG. 6 depicts a flowchart of an example process of a medicationdelivery vehicle (MDV) for authentication of medication delivery inaccordance with an illustrative embodiment.

DETAILED DESCRIPTION

The illustrative embodiments described herein generally relate to amethod, system, and computer program product for authentication of amedication delivery vehicle (MDV) with a user to facilitate release ofmedication contained therein. In one or more embodiments, a medicationdelivery vehicle (MDV) containing a medication encapsulated therein isprovided. In one or more embodiments, a medication delivery vehicle(MDV) is a delivery device or container configured to contain amedication or other substance for dispensing to a user when the MDV isingested by the user. In particular embodiments, the MDV is in a pill orcapsule form. In one or more embodiments, when the MDV is consumed by apatient, the MDV is wirelessly authenticated to an authentication deviceassociated with the patient, and the MDV allows the medication to bereleased into the patient's digestive tract to produce the desiredeffect upon the patient. In particular embodiments, the MDV utilizesradio frequency identification (RFID) tag and scanner wirelesstechnology to authenticate the MDV with the authentication device.

In one or more embodiments, if the MDV fails to authenticate, or asuitable authentication mechanism is not used with the MDV within apredefined period of ingesting the MDV, the MDV either remains intactwithout dispensing the medication contained therein, or triggers aneutralizing process to alter the chemical structure of the medicationto neutralize or otherwise reduce the effectiveness of the medicationencapsulated within the MDV.

In a particular embodiment, a processor of the MDV triggers a capacitorto release an electrical current to an electrically resistive mesh pouchcontaining the medication if the MDV fails to be authenticated. In theparticular embodiment, the release of the electrical current to the meshpouch causes heating of the mesh pouch and the medication containedtherein to a suitable temperature for a suitable time period resultingin neutralization of and/or reduction in the effectiveness of themedication. In one or more embodiments, the temperature is low enoughand the time period is short enough such that the patient is notnegatively affected by the neutralization process, yet the temperatureis high enough and the duration long enough to effectively neutralizethe medication to a sufficient degree. Guidance from pharmaceuticalmanufacturers recommend that most of the manufacturer's products bestored at a controlled room temperature of 68 degrees to 77 degreesFahrenheit (F), and that degradation may occur for products stored above86 degrees F. In a particular embodiment, the mesh pouch is heated to atemperature of 108 degrees Fahrenheit (F) for several seconds to renderthe medication inert and/or reduce the effectiveness of the medicationcontained within the mesh pouch.

Upon neutralization and/or reduction in effectiveness of the medicationdue to lack of authentication of the MDV, the medication has little orno effect on the patient. Within the scope of the illustrativeembodiments, neutralization of a medication includes a reduction in theeffectiveness of the medication. In one or more embodiments, regardlessof whether the MDV is authenticated, any undigested components of theMDV are safely passed from the patient's digestive system.

In one or more embodiments, an MDV including a prescribed medication isprovided to a user, such as a patient, to whom the medication isprescribed. In a particular embodiment, the MDV includes an RFID circuitconfigured to store a unique RFID public key or other identifierassociated with the user. In a particular embodiment, a medicationprovider, such as a pharmacy, encodes the RFID circuit of the MDV withthe unique public RFID associated with the user prior to providing theMDV to the user.

In one or more embodiments, the user has an authentication device, suchas an RFID device, that is configured to transmit a unique private key,such as a unique private RFID key, or another type of code related tothe identifier of the MDV. In a particular embodiment, theauthentication device is worn by the user, such as in a non-limitingwatch form-factor. In another particular embodiment, the authenticationdevice is implanted within the body of the user.

In one or more embodiments, the MDV has an outer layer dissolvable by afluid or substance present in the human body, such as saliva, thatcoats, covers, or otherwise contacts an external surface of the MDV. Inthe embodiment, an inner layer under the outer layer includes aplurality of electrical contacts in communication with an electroniccircuit of the MDV. In the embodiment, the MDV includes an isolated meshpouch storing the medication. In particular embodiments, the mesh pouchis constructed of an electrically resistive material such as anelectrically resistive refractory or inert/non-reactive metal. In theembodiment, the circuit is electrically connected with one or morecapacitors coupled to the mesh pouch. In one or more embodiments, theone or more capacitors are configured to store a charge to be providedto the mesh pouch in response to a signal from the circuit.

In an example operation of the MDV, a user places the MDV in the user'smouth and swallows the MDV. The outer layers of the MDV is dissolved bysaliva within the user's mouth and digestive track within a short periodof time such as several seconds. Upon dissolving of the outer layer,saliva or another fluid makes an electrically conductive path connectingthe electrical contacts disposed on the inner layer. The connecting ofthe contacts closes an electrical circuit indicating that the MDV hasbeen ingested by the user.

In a particular embodiment, the closed circuit between the electricalcontacts triggers the start of an internal timer within the circuit ofthe MDV. In another particular embodiment, the MDV includes a separatetimer circuit. Upon start of the timer, the wireless circuit of the MDVinterrogates the authentication device for the private RFID key oranother type of code associated with the user. In one embodiment, thecircuit passively waits for a signal from the authentication device.

If the wireless circuit receives the private key or anotheruser-specific code from the authentication device, and the circuitauthenticates the private key or code with the public key or identifierstored within the circuit within a predetermined time period, thecircuit stops the timer prior to the timer expiring. After a period oftime after the timer has stopped, stomach acids within the stomach ofthe user dissolve the mesh pouch thereby releasing the medication withinthe body of the user. As a result, the user receives the full benefitsof the medicine.

However, if the circuit does not receive the private key or code fromthe authentication device and/or does not authenticate the private keyor code with the public key or identifier stored within the circuitwithin the predetermined time period the timer expires. Responsive tothe timer expiring, the circuit triggers the one or more capacitors todischarge a current into the mesh pouch. In response, the mesh pouchheats up to above a threshold temperature, for example 108 degreeFahrenheit or greater, for at least a threshold period of time, forexample five seconds or more, to neutralize and/or reduce theeffectiveness of the medication stored within the mesh pouch. As aresult, the medication is rendered fully or partially ineffective to theuser.

Some embodiments provide for a system to ensure that medication is onlyfully effective on the patient for whom the medication is designated. Inparticular embodiments, e.g., when the medication is stolen or taken bysomeone other than the intended patient, the medication is neutralizedbefore release, thus eliminating the efficacy of the medication andcausing little or no reaction in the patient. In some embodiments,prescription drug thefts may be reduced and it can be ensured that theintended patient (e.g., an elderly person being cared for by another)will receive the medication.

The illustrative embodiments are described with respect to certain typesof medication delivery vehicles, pills, medications, keys, codes,identifiers, RFID technology, wireless technology, contents,transmissions, responses, devices, data processing systems,environments, components, and applications only as examples. Anyspecific manifestations of these and other similar artifacts are notintended to be limiting to the invention. Any suitable manifestation ofthese and other similar artifacts can be selected within the scope ofthe illustrative embodiments.

For example, while some embodiments are described with respect to RFIDtechnology, an embodiment may be adapted to use another suitablewireless communication technology within the scope of the embodiments.As another example, an embodiment may be adapted to use another suitablesonic, ultrasound, infrared, or other types of signals to trigger thecircuit in the MDV in a similar manner, and such adaptations arecontemplated within the scope of the illustrative embodiments. Anysuitable pair of coded data can be used in place of the RFID keys,identifiers, or codes described herein.

Furthermore, the illustrative embodiments may be implemented withrespect to any type of data, data source, or access to a data sourceover a data network. Any type of data storage device may provide thedata to an embodiment of the invention, either locally at a dataprocessing system or over a data network, within the scope of theinvention. Where an embodiment is described using a mobile device, anytype of data storage device suitable for use with the mobile device mayprovide the data to such embodiment, either locally at the mobile deviceor over a data network, within the scope of the illustrativeembodiments.

The illustrative embodiments are described using specific code, designs,architectures, protocols, layouts, schematics, and tools only asexamples and are not limiting to the illustrative embodiments.Furthermore, the illustrative embodiments are described in someinstances using particular software, tools, and data processingenvironments only as an example for the clarity of the description. Theillustrative embodiments may be used in conjunction with othercomparable or similarly purposed structures, systems, applications, orarchitectures. For example, other comparable mobile devices, structures,systems, applications, or architectures therefor, may be used inconjunction with such embodiment of the invention within the scope ofthe invention. An illustrative embodiment may be implemented inhardware, software, or a combination thereof.

The examples in this disclosure are used only for the clarity of thedescription and are not limiting to the illustrative embodiments.Additional data, operations, actions, tasks, activities, andmanipulations will be conceivable from this disclosure and the same arecontemplated within the scope of the illustrative embodiments.

Any advantages listed herein are only examples and are not intended tobe limiting to the illustrative embodiments. Additional or differentadvantages may be realized by specific illustrative embodiments.Furthermore, a particular illustrative embodiment may have some, all, ornone of the advantages listed above.

With reference to the figures and in particular with reference to FIGS.1 and 2 , these figures are example diagrams of data processingenvironments in which illustrative embodiments may be implemented. FIGS.1 and 2 are only examples and are not intended to assert or imply anylimitation with regard to the environments in which differentembodiments may be implemented. A particular implementation may makemany modifications to the depicted environments based on the followingdescription.

FIG. 1 depicts a block diagram of a network of data processing systemsin which illustrative embodiments may be implemented. Data processingenvironment 100 is a network of computers in which the illustrativeembodiments may be implemented. Data processing environment 100 includesnetwork 102. Network 102 is the medium used to provide communicationslinks between various devices and computers connected together withindata processing environment 100. Network 102 may include connections,such as wire, wireless communication links, or fiber optic cables.

Clients or servers are only example roles of certain data processingsystems connected to network 102 and are not intended to exclude otherconfigurations or roles for these data processing systems. Server 104and server 106 couple to network 102 along with storage unit 108.Software applications may execute on any computer in data processingenvironment 100. Clients 110, 112, and 114 are also coupled to network102. A data processing system, such as server 104 or 106, or client 110,112, or 114 may contain data and may have software applications orsoftware tools executing thereon.

Only as an example, and without implying any limitation to sucharchitecture, FIG. 1 depicts certain components that are usable in anexample implementation of an embodiment. For example, servers 104 and106, and clients 110, 112, 114, are depicted as servers and clients onlyas example and not to imply a limitation to a client-serverarchitecture. As another example, an embodiment can be distributedacross several data processing systems and a data network as shown,whereas another embodiment can be implemented on a single dataprocessing system within the scope of the illustrative embodiments. Dataprocessing systems 104, 106, 110, 112, and 114 also represent examplenodes in a cluster, partitions, and other configurations suitable forimplementing an embodiment.

RFID device 132 is an example of an authentication device describedherein. For example, RFID device 132 can take the form of a smartphone,a tablet computer, a laptop computer, client 110 in a stationary or aportable form, a wearable computing device, or any other suitabledevice. Any software application described as executing in another dataprocessing system in FIG. 1 can be configured to execute in RFID device132 in a similar manner. Any data or information stored or produced inanother data processing system in FIG. 1 can be configured to be storedor produced in RFID device 132 in a similar manner.

Medication delivery vehicle (MDV) 134 is an example of a medicationdelivery vehicle (MDV) described herein containing a medication to bedispensed to a user, such as a patient, that has ingested MDV 134.

Application 105 implements an embodiment described herein in the mannerof a remote server-based application or service. Application 105 maystore patent prescription information locally, or use storage unit 108that is accessible over network 102 to store patient prescriptioninformation in a secure manner within database 109.

Servers 104 and 106, storage unit 108, and clients 110, 112, and 114,and RFID device 132 may couple to network 102 using wired connections,wireless communication protocols, or other suitable data connectivity.Clients 110, 112, and 114 may be, for example, personal computers ornetwork computers.

In the depicted example, server 104 may provide data, such as bootfiles, operating system images, and applications to clients 110, 112,and 114. Clients 110, 112, and 114 may be clients to server 104 in thisexample. Clients 110, 112, 114, or some combination thereof, may includetheir own data, boot files, operating system images, and applications.Data processing environment 100 may include additional servers, clients,and other devices that are not shown.

In the depicted example, data processing environment 100 may be theInternet. Network 102 may represent a collection of networks andgateways that use the Transmission Control Protocol/Internet Protocol(TCP/IP) and other protocols to communicate with one another. At theheart of the Internet is a backbone of data communication links betweenmajor nodes or host computers, including thousands of commercial,governmental, educational, and other computer systems that route dataand messages. Of course, data processing environment 100 also may beimplemented as a number of different types of networks, such as forexample, an intranet, a local area network (LAN), or a wide area network(WAN). FIG. 1 is intended as an example, and not as an architecturallimitation for the different illustrative embodiments.

Among other uses, data processing environment 100 may be used forimplementing a client-server environment in which the illustrativeembodiments may be implemented. A client-server environment enablessoftware applications and data to be distributed across a network suchthat an application functions by using the interactivity between aclient data processing system and a server data processing system. Dataprocessing environment 100 may also employ a service orientedarchitecture where interoperable software components distributed acrossa network may be packaged together as coherent business applications.Data processing environment 100 may also take the form of a cloud, andemploy a cloud computing model of service delivery for enablingconvenient, on-demand network access to a shared pool of configurablecomputing resources (e.g. networks, network bandwidth, servers,processing, memory, storage, applications, virtual machines, andservices) that can be rapidly provisioned and released with minimalmanagement effort or interaction with a provider of the service.

With reference to FIG. 2 , this figure depicts a block diagram of a dataprocessing system in which illustrative embodiments may be implemented.Data processing system 200 is an example of a computer, such as servers104 and 106, or clients 110, 112, and 114 in FIG. 1 , or another type ofdevice in which computer usable program code or instructionsimplementing the processes may be located for the illustrativeembodiments.

Data processing system 200 is also representative of a data processingsystem or a configuration therein, such as data processing system 132 inFIG. 1 in which computer usable program code or instructionsimplementing the processes of the illustrative embodiments may belocated. Data processing system 200 is described as a computer only asan example, without being limited thereto. Implementations in the formof other devices, such as device 132 in FIG. 1 , may modify dataprocessing system 200, such as by adding a touch interface, and eveneliminate certain depicted components from data processing system 200without departing from the general description of the operations andfunctions of data processing system 200 described herein.

In the depicted example, data processing system 200 employs a hubarchitecture including North Bridge and memory controller hub (NB/MCH)202 and South Bridge and input/output (I/O) controller hub (SB/ICH) 204.Processing unit 206, main memory 208, and graphics processor 210 arecoupled to North Bridge and memory controller hub (NB/MCH) 202.Processing unit 206 may contain one or more processors and may beimplemented using one or more heterogeneous processor systems.Processing unit 206 may be a multi-core processor. Graphics processor210 may be coupled to NB/MCH 202 through an accelerated graphics port(AGP) in certain implementations.

In the depicted example, local area network (LAN) adapter 212 is coupledto South Bridge and I/O controller hub (SB/ICH) 204. Audio adapter 216,keyboard and mouse adapter 220, modem 222, read only memory (ROM) 224,universal serial bus (USB) and other ports 232, and PCI/PCIe devices 234are coupled to South Bridge and I/O controller hub 204 through bus 238.Hard disk drive (HDD) or solid-state drive (SSD) 226 and CD-ROM 230 arecoupled to South Bridge and I/O controller hub 204 through bus 240.PCI/PCIe devices 234 may include, for example, Ethernet adapters, add-incards, and PC cards for notebook computers. PCI uses a card buscontroller, while PCIe does not. ROM 224 may be, for example, a flashbinary input/output system (BIOS). Hard disk drive 226 and CD-ROM 230may use, for example, an integrated drive electronics (IDE), serialadvanced technology attachment (SATA) interface, or variants such asexternal-SATA (eSATA) and micro-SATA (mSATA). A super I/O (SIO) device236 may be coupled to South Bridge and I/O controller hub (SB/ICH) 204through bus 238.

Memories, such as main memory 208, ROM 224, or flash memory (not shown),are some examples of computer usable storage devices. Hard disk drive orsolid state drive 226, CD-ROM 230, and other similarly usable devicesare some examples of computer usable storage devices including acomputer usable storage medium.

An operating system runs on processing unit 206. The operating systemcoordinates and provides control of various components within dataprocessing system 200 in FIG. 2 . The operating system may be acommercially available operating system for any type of computingplatform, including but not limited to server systems, personalcomputers, and mobile devices. An object oriented or other type ofprogramming system may operate in conjunction with the operating systemand provide calls to the operating system from programs or applicationsexecuting on data processing system 200.

Instructions for the operating system, the object-oriented programmingsystem, and applications or programs, such as application 105 and 134 inFIG. 1 , are located on storage devices, such as in the form of code226A on hard disk drive 226, and may be loaded into at least one of oneor more memories, such as main memory 208, for execution by processingunit 206. The processes of the illustrative embodiments may be performedby processing unit 206 using computer implemented instructions, whichmay be located in a memory, such as, for example, main memory 208, readonly memory 224, or in one or more peripheral devices.

Furthermore, in one case, code 226A may be downloaded over network 201Afrom remote system 201B, where similar code 201C is stored on a storagedevice 201D. in another case, code 226A may be downloaded over network201A to remote system 201B, where downloaded code 201C is stored on astorage device 201D.

The hardware in FIGS. 1-2 may vary depending on the implementation.Other internal hardware or peripheral devices, such as flash memory,equivalent non-volatile memory, or optical disk drives and the like, maybe used in addition to or in place of the hardware depicted in FIGS. 1-2. In addition, the processes of the illustrative embodiments may beapplied to a multiprocessor data processing system.

In some illustrative examples, data processing system 200 may be apersonal digital assistant (PDA), which is generally configured withflash memory to provide non-volatile memory for storing operating systemfiles and/or user-generated data. A bus system may comprise one or morebuses, such as a system bus, an I/O bus, and a PCI bus. Of course, thebus system may be implemented using any type of communications fabric orarchitecture that provides for a transfer of data between differentcomponents or devices attached to the fabric or architecture.

A communications unit may include one or more devices used to transmitand receive data, such as a modem or a network adapter. A memory may be,for example, main memory 208 or a cache, such as the cache found inNorth Bridge and memory controller hub 202. A processing unit mayinclude one or more processors or CPUs.

The depicted examples in FIGS. 1-2 and above-described examples are notmeant to imply architectural limitations. For example, data processingsystem 200 also may be a tablet computer, laptop computer, or telephonedevice in addition to taking the form of a mobile or wearable device.

Where a computer or data processing system is described as a virtualmachine, a virtual device, or a virtual component, the virtual machine,virtual device, or the virtual component operates in the manner of dataprocessing system 200 using virtualized manifestation of some or allcomponents depicted in data processing system 200. For example, in avirtual machine, virtual device, or virtual component, processing unit206 is manifested as a virtualized instance of all or some number ofhardware processing units 206 available in a host data processingsystem, main memory 208 is manifested as a virtualized instance of allor some portion of main memory 208 that may be available in the hostdata processing system, and disk 226 is manifested as a virtualizedinstance of all or some portion of disk 226 that may be available in thehost data processing system. The host data processing system in suchcases is represented by data processing system 200.

With reference to FIG. 3 , this figure depicts a block diagram of anembodiment of a medication delivery vehicle (MDV) 134 in accordance withan illustrative embodiment. MDV 134 includes an outer layer 300configured to be dissolvable by saliva that coats and/or covers anexternal surface of MDV 134. In a particular embodiment, outer layer 300is configured to cover the entire outer surface of MDV 134. In stillanother embodiment, outer layer 300 may be configured to cover a portionof the outer surface of MDV 134. MDV 134 further includes an inner layer302 under outer layer 300. Inner layer 302 includes a plurality ofelectrical contacts 304 disposed upon and/or within inner layer 302.Electrical contacts 304 are in communication with a processor 306.Processor 304 is in further communication with a memory 308. Inparticular embodiments memory 308 is configured to store one or moreprogram instructions executable by processor 306 to perform one or moreof the functions of MDV 134 described herein.

In the embodiment, processor 306 is in further communication with RFIDcircuitry 310. In one or more embodiments, RFID circuit 310 isconfigured to store a public RFID encryption key associated with theuser, receive a private RFID encryption key associated with the userfrom RFID device 132, and authenticate the user using the private RFIDencryption key and the public RFID encryption key. Processor 306 isfurther in communication with a micro capacitor 312, and micro capacitor312 is in further communication with a mesh pouch 314. In one or moreembodiments, micro capacitor 312 is configured to store a charge currentto be provided to mesh pouch 314 in response to a signal from processor306. In particular embodiments, micro capacitor 312 may include one ormore of a graphine micro supercapacitor; a RuO2, Fe2O3, IrO2, TiS2capacitor; or a lithium doped carbon nanotube capacitor. In one or moreembodiments, processor 306, memory 308, RFID circuitry 310, and microcapacitor 312 are disposed upon a surface of or within inner layer 302.In an alternative embodiment, processor 306, memory 308, RFID circuitry310, and micro capacitor 312 can be disposed within an interior portionof MDV 134. In at least one embodiment, processor 306, memory 308, RFIDcircuitry 310, and micro capacitor 312 are integrated together as asingle component. In alternative embodiments, one or more of processor306, memory 308, RFID circuitry 310, and micro capacitor 312 can beseparate components.

In one or more embodiments, mesh pouch 314 contains a medication 316encapsulated therein. In particular embodiments, mesh pouch 314 isconstructed of an electrically resistive material such as anelectrically resistive, refractory, inert/non-reactive metal. In stillother particular embodiments, mesh pouch 314 may be constructed of anelectrically conductive material. In particular embodiments, mesh pouch314 may include a mesh of capillaries containing medication 316. In oneor more embodiments, mesh pouch 314 is configured to receive anelectrical current from micro capacitor 312 causing heating of meshpouch 314 and medication 316 contained therein to a predeterminedtemperature for a predetermined time period resulting in neutralizationof and/or reduction in the effectiveness of the medication. Although theembodiment illustrated in FIG. 3 is shown with processor 306, memory308, RFID circuit 310, and micro capacitor 312 within an interior of MDV134, in other embodiments one or more of processor 306, memory 308, RFIDcircuit 310, and micro-capacitor 312 can be disposed on inner layer 302or a surface of MDV 134.

With respect to FIG. 4 , this figure depicts a block diagram of anexample scenario for authentication of a medication delivery vehicle(MDV) within a simplified upper digestive tract 400 of a user inaccordance with an illustrative embodiment. Upper digestive tract 400includes a mouth 402, an esophagus 404, and a stomach 406. In theembodiment illustrated in FIG. 4 , the user is wearing an RFID device132 upon the body of a user. In the particular embodiment, RFID device132 is in a necklace and/or pendant form for wearing around a neck ofthe user. In other embodiments, RFID device 134 is worn on an arm orwrist of the user. In still other embodiments, RFID device 134 is notworn by the user but is instead located nearby to the user duringingestion of MDV 134. In the example scenario, the user ingests an MDV134 by placing MDV 134 within mouth 402 and swallowing MDV 134 to passthrough esophagus 404 to stomach 406. As described herein, saliva withinthe user's mouth dissolves the outer layer of MDV 134 and activates theelectrical contacts of MDV 134 to initiate a timer having apredetermined time period. MDV 134 then attempts to authenticate withRFID device 132. If MDV 134 successfully authenticates with RFID device132 within the predetermined time period, the timer stops and MDV 134dissolves within stomach 406 to release the medication contained withinMDV 134 into stomach 406.

If MDV 134 is unsuccessful in authenticating with RFID device 132 withinthe predetermined time period, MDV 134 heats the medication containedwithin MDV 134 at a predetermined temperature for a predetermined timeperiod to neutralize and/or otherwise reduce the effectiveness of themedication encapsulated within MDV 134 as described herein. In one ormore embodiments, any undigested components of MDV 134 are passedthrough the digestive tract of the user.

With respect to FIG. 5 , this figure depicts a flowchart of an exampleprocess 500 for authentication of a medication delivery vehicle (MDV) inaccordance with an illustrative embodiment. In block 502, a user ingestsmedication delivery vehicle 134. In block 504, saliva of the userdissolves an outer coating such as outer layer 300 of MDV 134. In block506, processor 306 detects a connection between electrical contacts 304caused by the saliva of the user. In block 508, processor 306 triggersthe start of a timer having a predetermined time period of duration. Inblock 510, RFID circuit 310 scan for an authentication signal from anauthentication device such as RFID device 132. In an alternativeembodiment, MDV 134 attempts to authenticate the user with a remotesystem, such as server 104, of FIG. 1 either directly or through anintermediary device such as RFID device 132.

In block 512, RFID circuit 310 and/or processor 306 determines whetherthe user is authenticated within the predetermined time period. Inparticular embodiments, RFID circuit 310 and/or processor 306authenticates the user using an private RFID encryption key receivedfrom RFID device 132 and a public RFID encryption key stored within MDV134. In a particular embodiment, RFID circuit 310 and/or processor 306authenticates the user by matching the private encryption key with thepublic encryption key stored within MDV 134. If the user isauthenticated within the predetermined time period, process 500continues to block 514. In block 512, processor 306 stops the timer. Inblock 516, mesh pouch 314 of MDV 134 is dissolved within the stomach ofthe user. In block 518, medication 316 is released into the stomach ofthe user to be absorbed by the body of the user and process 500 ends.

If in block 512, RFID circuit 310 and/or processor 306 determines thatthe user is not authenticated within the predetermined time period,processor 306 triggers discharge of an electrical current from microcapacitor 312 to the electrically conductive and/or electricallyresistive mesh pouch 314 in block 520. In block 522, mesh pouch 314heats to a predetermined temperature for a predetermined time period inresponse to receiving the electrical current from micro capacitor 312.In 524, medication 316 is neutralized and/or reduced in effectivenesspouch. As a result, medication 316 is rendered fully or partiallyineffective to the user when dissolved by the stomach of the user. Theprocess 500 then ends.

With respect to FIG. 6 , this figure depicts a flowchart of an exampleprocess 600 of medication delivery vehicle (MDV) 134 for authenticationof a medication delivery in accordance with an illustrative embodiment.In the embodiment of FIG. 6 , a user ingests MDV 134 and saliva of theuser dissolves outer layer 300 of MDV 134. In block 602, processor 306detects a connection between electrical contacts 304 caused by thesaliva of the user. In block 604, processor 306 triggers the start of atimer having a predetermined time period of duration. In block 608, RFIDcircuit 310 scan for an authentication signal from an authenticationdevice such as RFID device 132.

In block 608, RFID circuit 310 and/or processor 306 determines whetherthe user is authenticated within the predetermined time period. Inparticular embodiments, RFID circuit 310 and/or processor 306authenticates the user using an private RFID encryption key receivedfrom RFID device 132 and a public RFID encryption key stored within MDV134. If the user is authenticated within the predetermined time period,process 600 continues to block 610. In block 610, processor 306 stopsthe timer. Accordingly, when mesh pouch 314 of MDV 134 is dissolvedwithin the stomach of the user, medication 316 is released into thestomach of the user to be absorbed by the body of the user and process600 ends.

If in block 608, RFID circuit 310 and/or processor 306 determines thatthe user is not authenticated within the predetermined time period,processor 306 triggers discharge of an electrical current from microcapacitor 312 to the electrically conductive and/or electricallyresistive mesh pouch 314 in block 612 and the process 600 ends. As aresult, mesh pouch 314 heats to a predetermined temperature for apredetermined time period in response to receiving the electricalcurrent from micro capacitor 312, and medication 316 is neutralizedand/or reduced in effectiveness pouch. Accordingly medication 316 isrendered fully or partially ineffective to the user when dissolved bythe stomach of the user.

Although various embodiments describe medication as being stored withinmedication delivery vehicle 134, it should be understood that in otherembodiments other types of substances may be stored in a deliveryvehicle that is desired to be authenticated with a user before the usermay use the substance.

Thus, a computer implemented method, system or apparatus, and computerprogram product are provided in the illustrative embodiments forauthentication of a delivery vehicle with a user to facilitate releaseof medication or any other substance contained therein and other relatedfeatures, functions, or operations. Where an embodiment or a portionthereof is described with respect to a type of device, the computerimplemented method, system or apparatus, the computer program product,or a portion thereof, are adapted or configured for use with a suitableand comparable manifestation of that type of device.

Where an embodiment is described as implemented in an application, thedelivery of the application in a Software as a Service (SaaS) model iscontemplated within the scope of the illustrative embodiments. In a SaaSmodel, the capability of the application implementing an embodiment isprovided to a user by executing the application in a cloudinfrastructure. The user can access the application using a variety ofclient devices through a thin client interface such as a web browser(e.g., web-based e-mail), or other light-weight client-applications. Theuser does not manage or control the underlying cloud infrastructureincluding the network, servers, operating systems, or the storage of thecloud infrastructure. In some cases, the user may not even manage orcontrol the capabilities of the SaaS application. In some other cases,the SaaS implementation of the application may permit a possibleexception of limited user-specific application configuration settings.

The present invention may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The computer program product may include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

What is claimed is:
 1. A method comprising: determining, by a circuit ofa delivery device, the delivery device containing a substanceencapsulated in a mesh, that the delivery device has been ingested;initiating, in the circuit of the delivery device subsequent toingestion of the delivery device, a timer set of expire in apredetermined time period; monitoring, in the circuit of the deliverydevice during the predetermined time period, for receipt of auser-specific authentication code; stopping, responsive to determiningthat a user-specific authentication code received within thepredetermined time period is valid, the timer; and applying, responsiveto expiration of the timer, prior to dissolution of the mesh, anelectrical current to the mesh containing the substance, the electricalcurrent reducing an effectiveness of the substance.
 2. The method ofclaim 1, wherein a radio frequency identification (RFID) circuit of thedelivery device receives the user-specific authentication code.
 3. Themethod of claim 1, wherein the applying the electrical current comprisesdischarging a capacitor into the mesh configured to encapsulate thesubstance.
 4. The method of claim 3, wherein the mesh comprises anelectrically conductive mesh.
 5. The method of claim 1, whereindetermining that the delivery device has been ingested includesdetermining that a closed circuit exists between a plurality ofelectrical contacts of the delivery device.
 6. The method of claim 5,wherein the closed circuit is caused by saliva.
 7. The method of claim1, wherein the user-specific authentication code comprises a privateencryption key.
 8. The method of claim 7, wherein an identifier storedwithin the delivery device comprises a public encryption keycorresponding to the private encryption key.
 9. The method of claim 8,wherein determining whether the user-specific authentication code isvalid includes matching the private encryption key with the publicencryption key.
 10. The method of claim 8, wherein the user-specificauthentication code is received from an authentication device associatedwith a user.
 11. The method of claim 10, wherein the authenticationdevice is configured to be worn by the user.
 12. The method of claim 10,wherein the authentication device is implanted within the user.
 13. Themethod of claim 1, wherein the substance is a medication.
 14. A computerusable program product comprising one or more computer-readablenon-transitory storage devices, and program instructions stored on atleast one of the one or more storage devices, the stored programinstructions comprising: program instructions to determine, by a circuitof a delivery device, the delivery device containing a substanceencapsulated in a mesh, that the delivery device has been ingested;program instructions to initiate, in the circuit of the delivery devicesubsequent to ingestion of the delivery device, a timer set of expire ina predetermined time period; program instructions to monitor, in thecircuit of the delivery device during the predetermined time period, forreceipt of a user-specific authentication code; program instructions tostop, responsive to determining that a user-specific authentication codereceived within the predetermined time period is valid, the timer; andprogram instructions to apply, responsive to expiration of the timer,prior to dissolution of the mesh, an electrical current to the meshcontaining the substance, the electrical current reducing aneffectiveness of the substance.
 15. The computer usable program productof claim 14, wherein a radio frequency identification (RFID) circuit ofthe delivery device receives the user-specific authentication code. 16.The computer usable program product of claim 14, wherein applying theelectrical current comprises discharging a capacitor into the meshconfigured to encapsulate the substance.
 17. The computer usable programproduct of claim 14, wherein the program instructions are stored in theat least one computer readable storage device in a data processingsystem, and wherein the program instructions are transferred over anetwork from a remote data processing system.
 18. The computer usableprogram product of claim 14, wherein the program instructions are storedin the at least one computer readable storage device in a server dataprocessing system, and wherein the program instructions are downloadedover a network to a remote data processing system for use in a computerreadable storage device associated with the remote data processingsystem.
 19. A computer system comprising one or more processors, one ormore computer-readable memories, and one or more computer-readablestorage devices, and program instructions stored on at least one of theone or more storage devices for execution by at least one of the one ormore processors via at least one of the one or more memories, the storedprogram instructions comprising: program instructions to determine, by acircuit of a delivery device, the delivery device containing a substanceencapsulated in a mesh, that the delivery device has been ingested;program instructions to initiate, in the circuit of the delivery devicesubsequent to ingestion of the delivery device, a timer set of expire ina predetermined time period; program instructions to monitor, in thecircuit of the delivery device during the predetermined time period, forreceipt of a user-specific authentication code; program instructions tostop, responsive to determining that a user-specific authentication codereceived within the predetermined time period is valid, the timer; andprogram instructions to apply, responsive to expiration of the timer,prior to dissolution of the mesh, an electrical current to the meshcontaining the substance, the electrical current reducing aneffectiveness of the substance.